ci: add on-demand autotls beekeeper workflow#5478
Conversation
|
Additionally, instead of running it manually only, we can add a Trade-off: merge_group runs cannot accept the workflow inputs (those exist only for workflow_dispatch), so the queue always uses the BEEKEEPER_BRANCH / BEELOCAL_BRANCH defaults hardcoded in this file. In practice this is the correct way, because all dependecies should be merged earlier. wdyt @acud @akrem-chabchoub ? |
| - name: Test retrieval (autotls) | ||
| run: timeout ${TIMEOUT} beekeeper check --cluster-name local-dns-autotls --checks=ci-retrieval | ||
| - name: Test autotls | ||
| run: timeout ${TIMEOUT} beekeeper check --cluster-name local-dns-autotls --checks=ci-autotls |
There was a problem hiding this comment.
Should we add at the end an if: failure() step for debuging?
There was a problem hiding this comment.
No need. We can always test locally in case it fails.
Checklist
Description
Adds
.github/workflows/beekeeper-autotls.yml— a manually triggered workflowfor the AutoTLS beekeeper checks (
ci-pingpong,ci-full-connectivity,ci-retrieval,ci-autotls) against thelocal-dns-autotlscluster.The AutoTLS cluster is slow to start, so this workflow deliberately does not
run on push/PR commits. It runs only on
workflow_dispatch, from the Actionstab via "Run workflow":
an explicit
refinput.beekeeper_branchinput (defaultmaster) — beekeeper tooling/checks branch.beelocal_branchinput (defaultmain) — beelocal cluster-setup branch.The branch inputs let you point at the beekeeper/beelocal feature branches that
define
local-dns-autotls/ci-autotlswithout editing the workflow.beekeeper.ymlis left unchanged. This replaces the approach in #5350 (whichwired AutoTLS into the per-commit PR flow), so #5350 can be closed.
Open API Spec Version Changes (if applicable)
Motivation and Context (Optional)
Related Issue (Optional)
Screenshots (if appropriate):
AI Disclosure